another idea would be to have a

type Spinner[T any] struct {
  action func () T
  // ..

and maybe a

type Spinner2[T any, Q any] struct {
  action func() (T, Q)
}

the later being most commonly used as Spinner2[Something, error] I would guess, maybe even worth making the second arg an error always.

@maaslalani I reworked some stuff:

• run the action as part as a tea.Cmd
• improve handling when having only ctx, only action, both, or neither

I think this might also fix #196

one bad thing about this, is that it might be a breaking change 🤔

Can't you support both signature with generics? 🤔

also added the feature from #172 here

I think I'm missing something obvious here - what's wrong with how we're currently handling actions and how does this change improve that?

I think I'm missing something obvious here - what's wrong with how we're currently handling actions and how does this change improve that?

if i recall correctly, if you passed both a context and a function it didn't work properly, that's fixed here